Skip to content

General fixes & improvements#1976

Open
Oaphi wants to merge 28 commits intodevelopfrom
0valt/common-fixes
Open

General fixes & improvements#1976
Oaphi wants to merge 28 commits intodevelopfrom
0valt/common-fixes

Conversation

@Oaphi
Copy link
Member

@Oaphi Oaphi commented Feb 3, 2026

closes #1968 (the label is now configurable via locale strings):

Screenshot from 2026-02-03 17-39-50

closes #1971:

Screenshot from 2026-02-03 18-17-51 Screenshot from 2026-02-03 18-18-02 Screenshot from 2026-02-03 18-18-15

closes #1975 - comment threads now use the priority_order common scope regardless of whether they are initially loaded or expanded via the "show more" button (note that we still order by updated_at and not last_activity_at - we should switch to the latter when we can).

closes #1970:

image

closes #1965 (see below);
closes #1966 (see below);
closes #1884 (we now simply use Moment.js to format timestamps - note the new format and preserved relative time):

2026-02-05_14-24

closes #1977 (also exposes MaxUploadSize to client-side code as QPixel.MAX_UPLOAD_SIZE):
Screenshot from 2026-02-05 16-19-05

closes #1969 (with existing threads and no threads respectively):

image image

closes #1671 (new site setting: MaxRequestBodySize):
image

@codecov
Copy link

codecov bot commented Feb 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.96%. Comparing base (fb4d5da) to head (b72d3a4).

Additional details and impacted files
Components Coverage Δ
controllers 75.57% <ø> (ø)
helpers 85.08% <100.00%> (+0.02%) ⬆️
jobs 81.48% <ø> (ø)
models 93.03% <100.00%> (-0.01%) ⬇️
tasks 61.11% <ø> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Oaphi Oaphi requested review from a team, cellio and trichoplax February 3, 2026 15:59
@cellio
Copy link
Member

cellio commented Feb 3, 2026

Tested:

  • comment label (1968)
  • search width (1971)
  • thread order (1975)
  • profile stats alignment (1970)
  • notification times (1965)
  • inbox date format (1966)
  • large avatar images (1977)
  • new comment wording (1969)

What user testing, if any, applies for #1884 and #1671?

Oaphi added 20 commits February 3, 2026 20:09
@Oaphi Oaphi marked this pull request as ready for review February 7, 2026 18:28
Comment on lines 219 to 236
def cleanup_site_settings
to_remove = []

$site_settings_map.each do |community_id, names|
stale_settings = SiteSetting.unscoped
.where(community_id: community_id)
.where.not(name: names)
to_remove.push(*stale_settings)
end

return unless to_remove.any?

ActiveRecord::Base.transaction do
to_remove.each(&:destroy!)
end

puts "#{SiteSetting.model_name}: removed #{to_remove.size}"
end
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After this PR is merged, we'll start automatically removing SiteSettings that are no longer present in seeds. My hope is that it'll evolve into a proper cleanup step in the future and then into a full solution for dynamically changing seeds.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: if a setting is no longer in seeds but is in the DB, then code that still checks for that setting would continue to work in existing deployments and fail in new ones. How do we make sure that there's no referring code before removing, and especially auto-removing, a setting? I love having cleanup but do want to make sure we only clean up truly unused stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

3 participants